Search results for "Feature-oriented domain analysis"
showing 7 items of 7 documents
Adding Domain Analysis to Software Development Method
2002
The researchers in the field of software development regard the reuse of components as one possible approach when creating quality software in less time and with fewer people. When components are used and created in the software development, one critical success factor is the use of domain analysis (DA). We report an action case study where the DA technique is first integrated into an existing software development method and then refined based on the experience of using it in a pilot project. The results indicate that our approach produces reusable components across a company-wide domain and eases the use of them in other development projects within domain.
Comprehensive System for Systematic Case-Driven Software Reuse
2010
Reuse of software artifacts (blueprints and code) is normally associated with organising a systematic reuse framework most often constructed for a specific problem domain. In this paper we present a system (language, tool, reuse process) where software reuse is based on building and retrieving of so-called software cases (large compound artifacts) that can be reused between domains. The system is opportunistic in that software cases result from usual (non-reuse oriented) activities where also semantic information is added. This information is used to support regular development but may serve later to retrieve software cases. Having this common semantic basis, we can organise a systematic cr…
Developing Software with Domain-Driven Model Reuse
2015
This chapter presents an approach to software development where model-driven development and software reuse facilities are combined in a natural way. It shows how model transformations building a Platform Independent Model (PIM) can be applied directly to the requirements specified in RSL by domain experts. Further development of the software case (PSM, code) is also supported by transformations, which in addition ensure a rich traceability within the software case. Alternatively, the PSM model and code can also be generated directly from requirements in RSL, thus providing fast development of the final code of at least a system prototype in many situations. The reuse support relies on a si…
Using Hierarchies to Adapt Domain Analysis to Software Development
2001
Software development strives toward increasing the amount and quality of the software and at the same time decreasing the costs and development time. One approach to achieve these diverse goals is the systematic software reuse (Biggerstaff and Richter, 1987). In the reuse-oriented software development the key success factor is domain analysis (DA) (Arango, 1989; Lam and McDermid, 1997; Prieto-Diaz, 1994). DA is a process through which information used in software development is identified, captured, and organized with the purpose of making it reusable when creating new systems (Prieto-Diaz, 1990). While the traditional development methods (e.g., Jaaksi et al.,1999; Jacobson et al., 1999) fo…
Domain-Driven Reuse of Software Design Models
2011
This chapter presents an approach to software development where model driven development and software reuse facilities are combined in a natural way. The basis for all of this is a semiformal requirements language RSL. The requirements in RSL consist of use cases refined by scenarios in a simple controlled natural language and the domain vocabulary containing the domain concepts. The chapter shows how model transformations building a platform independent model (PIM) can be applied directly to the requirements specified in RSL by domain experts. Further development of the software case (PSM, code) is also supported by transformations, which in addition ensure a rich traceability within the s…
Do we need metamodels AND ontologies for engineering platforms?
2006
In this paper we show how the joint use of metamodeling and ontologies allows to describe domain knowledge for a complex domain. Ontologies are used as stabilized descriptions of a business domain while metamodels allow a fine description of the domain (to be constructed in the initial phases of modeling). We propose to use an ontology for early categorization, i.e., as a "natural" complement of the formal system that is induced by the metamodel.